Energy-aware job scheduling for cluster environments

ABSTRACT

A job scheduler can select a processor core operating frequency for a node in a cluster to perform a job based on energy usage and performance data. After a job request is received, an energy aware job scheduler accesses data that specifies energy usage and job performance metrics that correspond to the requested job and a plurality of processor core operating frequencies. A first of the plurality of processor core operating frequencies is selected that satisfies an energy usage criterion for performing the job based, at least in part, on the data that specifies energy usage and job performance metrics that correspond to the job. The job is assigned to be performed by a node in the cluster at the selected first of the plurality of processor core operating frequencies.

RELATED APPLICATIONS

This continuation application claims the benefit under 35 U.S.C. §120 ofU.S. Patent Application Ser. No. 12/917,421 filed Nov. 1, 2010. U.S.patent application Ser. No. 12/917,421 claims priority to EuropeanPatent Application No. 10305449.0, which was filed on Apr. 20, 2010.

BACKGROUND

Embodiments of the inventive subject matter generally relate to thefield of energy conservation aware computing, and, more particularly, toenergy-aware job scheduling for cluster environments.

Managing power consumption has become a serious concern to many highperformance computing (HPC) data centers where large clusters are usedfor running parallel applications. The performance characteristics of aparallel application can range from processor intensive to memorybandwidth intensive. These performance characteristics affect powerconsumption. The Active Energy Manager (AEM) tool provides acomprehensive view of energy consumption in a data center. The AEM toolmeasures, monitors, and manages energy components built into systems.The AEM tool measures and monitors components by collecting powerinformation of devices plugged into a power distribution unit. The AEMtool manages energy components with power capping and power savingsmode.

SUMMARY

Embodiments include a method and a computer program product that accessdata that specifies energy usage and job performance metrics thatcorrespond to a job and a plurality of processor core operatingfrequencies. The job has been requested of a cluster. A first of theplurality of processor core operating frequencies is selected thatsatisfies an energy usage criterion for performing the job based, atleast in part, on the data that specifies energy usage and jobperformance metrics that correspond to the job. The job is assigned tobe performed by a node in the cluster at the selected first of theplurality of processor core operating frequencies.

BRIEF DESCRIPTION OF THE DRAWINGS

The present embodiments may be better understood, and numerous objects,features, and advantages made apparent to those skilled in the art byreferencing the accompanying drawings.

FIG. 1 depicts an example conceptual diagram of a system for selectingfrequencies to perform jobs based on energy usage and performancemetrics.

FIGS. 2 and 3 are flowcharts depicting example operations for selectingfrequencies to run jobs based on energy usage and performance data.

FIG. 4 is a flowchart depicting example operations for determiningcoefficients of a regression model.

FIG. 5 depicts an example computer system with an energy aware jobscheduler

DESCRIPTION OF EMBODIMENT(S)

The description that follows includes exemplary systems, methods,techniques, instruction sequences and computer program products thatembody techniques of the present inventive subject matter. However, itis understood that the described embodiments may be practiced withoutthese specific details. For instance, although examples refer toreducing frequencies of nodes in a cluster below a default processorcore operating frequency, embodiments can increase the frequencies abovethe default processor core operating frequency. In other instances,well-known instruction instances, protocols, structures and techniqueshave not been shown in detail in order not to obfuscate the description.

The description herein uses the terms “job” and “node.” The term “job”refers to a task or tasks performed by a node. Examples of a taskinclude searching a database, updating a record(s) in a database,performing a computation(s), backing up data, compressing data, scanningdata, analyzing data, etc. A node can perform a job with a variety oftechniques include: executing a program or batch of programs, awakeningan executing instance of a program(s) (“process”), passing aparameter(s) to a process, etc. The node may execute programs serially,in parallel, or a combination thereof. Processes may cooperate orcoordinate with each other to perform a job or task of a job. The term“node” is used herein to refer to a computational entity within a groupor cluster of nodes that can execute a program(s). Examples of a nodeinclude a core of a processor, a processor, an application specificintegrated circuit, a blade server, etc.

Power management techniques react to current energy usage (e.g., bypowering down nodes, scaling down frequencies, etc.) rather thanproactively manage power use based on predicted energy usage forperforming a job. The predicted energy usage is based on energy usageand performance data collected prior to performing the job. When a jobscheduler receives a job, the job scheduler determines whether therequested job (or a similar job) has been previously performed by one ormore nodes in a cluster. If the job has been performed previously, thejob scheduler (or an entity that can communicate with the job scheduler)retrieves actual energy usage (e.g., watts consumed) and actual jobperformance data (e.g., time to completion) for the previously performedjob. The job scheduler can also retrieve or generate estimated energyusage and/or job performance data at different processor core operatingfrequencies of a node(s) in the cluster. The job scheduler can analyzethe energy usage and job performance data to determine a processor coreoperating frequency for performing the job while conserving energy. Ajob criterion, (e.g., a policy that governs the job) may also influenceselection of the processor core operating frequency to satisfy thecriterion. The job scheduler assigns the job to one or more nodes in thecluster to be performed at the determined processor core operatingfrequency.

FIG. 1 depicts an example conceptual diagram of a system for selectingfrequencies to perform jobs based on energy usage and performancemetrics. The system includes a cluster comprising four nodes—node 1 109,node 2 117, node 3 125, and node N 133. The nodes 109, 117, 125, and 133respectively comprise control processes 111, 119, 127, and 135, andfurther comprise cores 1 113, 121, 129, and 137, respectively and cores2 115, 123, 131, and 139, respectively. The cores 1 113, 121, 138 and137 and cores 2 115, 123, 131, and 139 can operate at multiple processorcore operating frequencies. An initial/default processor core operatingfrequency is specified for the cores 1 113, 121, 138 and 137 and cores 2115, 123, 131, and 139. For example, oscillators associated with each ofthe nodes 109, 117, 125, and 133 provide output to control frequency ofthe cores 1 113, 121, 138 and 137 and cores 2 115, 123, 131. Initially,the frequency is a default processor core operating frequency. Thedefault processor core operating frequency can be divided/multiplied todecrease/increase the frequency (“frequency scaling”) of the cores 1113, 121, 138 and 137 and cores 2 115, 123, 131, and 139. Thefrequencies can be varied within a certain operating range of the cores1 113, 121, 138 and 137 and cores 2 115, 123, 131, and 139 and thedivision/multiplication of the default processor core operatingfrequency can be based on a certain factor. For example, the defaultprocessor core operating frequency of core 1 113 and core 2 115 is 4GHz. The core 1 113 and core 2 115 can operate in the range of 2 GHz to8 GHz. The default processor core operating frequency can bedivided/multiplied by factors of 2, so supported frequencies for thecore 1 113 and the core 2 115 are 2 GHz, 4 GHz, and 8 GHz. Embodimentsare not limited to any of these example illustrations relating toprocessor core operating frequency. It should be appreciated that avariety of designs exist and are possible for cores, which could affectany one of the operating range, degree of frequency scaling, andmechanism for frequency scaling. For brevity, the description will referto those frequencies that fall within an operating range of a core(s) orthat are in accordance with a specification of a core(s) as “supportedfrequencies.”

The cluster is associated with a server 101 that manages the cluster.The server 101 is connected to a storage device 105 that hosts aperformance and energy usage database 107. The server 101 comprises anenergy aware energy aware job scheduler 103 that assigns jobs to thenodes 109, 117, 125, and 133 based on analysis of energy usage and jobperformance data. The energy aware job scheduler 103 comprises an energyawareness module 102 and a job assignor 104. FIG. 1 depicts the energyaware job scheduler 103 as comprising the distinct modules (e.g.,functions, procedures, routines, methods of a class, etc.) forillustrative purposes. Depicting the energy awareness module 102conceptually illustrates the functionality for analyzing energy usageand job performance data, and selecting a processor core operatingfrequency accordingly. Depicting the job assignor 104 conceptuallyillustrates the functionality for assigning jobs to nodes in accordancewith the operations/output of the energy awareness module 102. The namesof the modules attempt to reflect the illustrated functionality of themodules within the limited space of the drawing sheet, and should not beused to limit embodiments. Embodiments can implement the code for anenergy aware job scheduler in accordance with a variety of programmingpractices, programming styles, programming paradigms, etc. For example,the functionality can range from being more modular (e.g., separatemodules retrieve data, analyze data, and select a processor coreoperating frequency) to not modular (e.g., a singleroutine/function/procedure performs all functionality). Furthermore,embodiments can implement one or more distinct programs. For example,separate programs can be implemented to analyze job performance andenergy usage data and to select a processor core operating frequency.These separate programs can then communicate with a job scheduler toassign jobs in accordance with the analysis and selected processor coreoperating frequency.

Returning to FIG. 1, the energy aware job scheduler 103 selects one ormore nodes to perform the job based on resources (e.g., amount ofmemory, network bandwidth, etc.) indicated for the job and availabilityof the nodes. The energy awareness module 102 determines a processorcore operating frequency for the selected node(s) based on a jobcriterion (e.g., maximum run time, deadline for completing the job,etc.) and energy usage and performance data collected during a previousperformance of the job. The energy aware job scheduler 103 alsodetermines a processor core operating frequency based on a policy forthe system (e.g., a monthly energy consumption policy for the overallsystem, a daily energy consumption limit per node in the system, etc.).The job assignor module 102 then assigns the job to the node(s).Assignment of a job to a node can be implemented with a variety oftechniques. Examples of job assignment techniques include: transmittingan operation code to a listening process, which could be the controlprocess, on the node; transmitting, to a control process on the node, areference to a program to be executed, instantiating a control processon a management system, which could be the same system hosting the jobscheduler, to remotely control a node to perform a job; using a remoteprocedure call; communicating a command message to a control process onthe node; and forwarding a job descriptor to a node to be parsed by acontrol process on the node. The control processes 111, 119, 127, and135 can be instances of a module(s) of the energy aware job scheduler103, and may be locally instantiated. The code for the control processes111, 119, 127, and 135 may be stored locally also (e.g., installed ateach node, distributed from a remote management system, etc.). Thecontrol processes 111, 119, 127, and 135 can be utilized to collectenergy usage and job performance data while jobs are being performed bythe respective nodes 109, 117, 125, and 137. Embodiments can alsocollect energy usage and job performance data with other processesindependent of the job scheduler. The collected energy usage and jobperformance data is stored in the performance and energy usage database107. Prior to job assignment, coincident to job assignment, or prior toperforming a job, a control process sets the processor core operatingfrequency to the processor core operating frequency selected by the jobscheduler. For instance, the control processes 111, 119, 125, and 135can utilize an application programming interface (API) to change theprocessor core operating frequency of the respective cores. Embodimentsare not limited to an API, though. Embodiments can execute a proprietaryscript to adjust the processor core operating frequency, can set a valuein hardware that adjusts the processor core operating frequency, etc.

At stage A, the energy aware job scheduler 103 receives a job. Forexample, the energy aware job scheduler 103 receives a job descriptorfile specifying the programs to be executed and the resources that arenecessary for the programs to execute. Included in the specifiednecessary resources may be, for example, an amount of memory, types ofprocessors, storage space, software licenses, etc. A job request canoriginate from a plethora of sources. A job request may originate froman executing program that accepts information entered into a userinterface by a user at a system that may or may not be the system thathosts the job scheduler. A job request may originate from a process thatmanages a list of job requests scheduled in advance. For example, asystem administrator may schedule a backup job and virus scan job everySaturday at 3:00 am with a user interface of a job schedulingapplication. At 3:00 am on Saturday, a process associated with thescheduling application generates a job request. As another example, auser can enter information for a job request into a web browserinterface and submit the information via a web browser. A process of anonline service provider processes the information and generates a jobrequest.

At stage B, the energy awareness module 103 accesses the database 107 todetermine whether the job has been performed and to retrieve energyusage and job performance data that corresponds to the job. The energyawareness module 103 searches the performance and energy usage database107 for an indication of the job (e.g., an identifier of the job, a jobtype or class, etc) responsive to receiving a job request. Inclusion inone or more records in the performance and energy usage database 107indicates that the job has been previously performed in the clusterassociated with the server 101. Embodiments are not limited to searchinga database of job performance and energy usage data to determine whethera job has been previously performed. Embodiments can maintain variousinformation in a structure(s) that indicates jobs previously performedincluding: a structure that indicates jobs performed in the clusterwithin a preceding time period; a structure that indicates the last njobs performed; separate structures for different classes of jobs, eachindicating the last n jobs of that class performed; etc.

An example record 151 from the database 107 is illustrated in FIG. 1 asindicating a job identifier, nodes that performed the job, job class,and job performance data and energy usage data at three differentprocessor core operating frequencies. The example record 151 indicates ajob identifier “Job1”, nodes Node 1 and Node 2 as having performed Job1,and a job class “Security Scan.” The record 151 indicates the threesupported processor core operating frequencies as 500 MHz, 1 GHz, and1.2 GHz. At 500 MHz, the job performance and energy usage datarespectively specify 3000 seconds and 70 watts. At 1 GHz, the jobperformance and energy usage data respectively specify 2100 seconds and90 watts. At 1.2 GHz, the job performance data and energy usagerespectively specify 1800 seconds and 100 watts. Assuming that therequested job identifier is Job1, the energy awareness module 102determines that the requested job has been performed previously. If theenergy awareness module 102 determined that the requested job had notbeen previously performed by the cluster or had not been previouslyperformed within a window of time, then, in response, the energyawareness module 102 can determine whether a similar job had beenperformed on the cluster based on the job request. Embodiments canimplement a performance and energy usage database with more information,less information, or different information than depicted in the examplerecord 151 of FIG. 1. Additional information can be used to determine apreviously performed job as similar to a requested job. For example, theenergy awareness module 102 can search the performance and energydatabase 107 for any one or more of a job type, job class, program namesassociated with the requested job, performance characteristics of therequested job (e.g., core intensive, memory intensive, I/O intensive,both I/O and core intensive, etc.). Embodiments can set a threshold orcriterion for accepting an entry for a previously performed job assimilar to the requested job (e.g., a minimum number of programs thatmatch). Further, embodiments are not limited to determining that a jobor similar job has been previously performed by a cluster with aperformance and energy usage database. Embodiments can access otherdata, such as a log or job request history of operations, to determinewhether a job or similar job has been previously performed.

In response to receiving the job request and determining that the jobJob1 has been previously performed (or that Job1 is sufficiently similarto the requested job), the energy awareness module 102 retrieves energyusage and job performance data from the record 151. The energy usage andjob performance data can comprise estimates of energy usage and jobperformance data for one or more of the supported frequencies of thenodes 109, 117. For example, the control processes 111 and 119 canutilize an energy use measuring/monitoring tool, such as the ActiveEnergy Manager from IBM®, to determine the power consumed by the nodes109 and 117, respectively. The energy awareness module 102 determinesaggregate power consumption based on collecting the power consumptionfrom the control processes 109 and 117. The energy awareness module 102can also computes the completion time from the start time and end timeof the job. The energy awareness module 102 can use the powerconsumption and completion time at 1.2 GHz to estimate power consumptionand completion times at 1 GHz and 500 MHz on nodes 109, 117. Embodimentscan replace estimated job performance and energy usage data with actualjob performance and energy usage data if/when the job is performed atthe other frequencies. For example, on a second performance of the job,the energy awareness module 102 selects 500 MHz to perform the job.During the second performance, the energy aware job scheduler 103 candetermine actual energy usage and job performance. An energy usemonitoring/measuring tool can update the energy usage and jobperformance data to include the actual energy usage and performance at500 MHz. The energy awareness module 102 could then use the actualenergy usage and job performance data at 500 MHz when selecting aprocess core operating frequency for future performance of the job.

At stage C, the energy awareness module 102 utilizes the energy usageand performance data to select a frequency to run the job according to aperformance policy. The performance policy can be included in a jobdescription file associated with the job. For example, if theperformance policy indicates that energy consumption should be minimizedwithout regard to application performance (e.g., completion time), theenergy awareness module 102 selects the processor core operatingfrequency based on the lowest energy usage indicated in the energy usagedata. As another example, if the performance policy indicates a minimumperformance to be maintained while minimizing energy consumption, theenergy awareness module 102 selects the processor core operatingfrequency associated with the lowest energy usage indicated in theenergy usage data that corresponds to a performance indicated in theperformance data that is greater than or equal to the specified minimumperformance.

At stage D, the job assignor module 104 assigns the job to nodes in thecluster and sets the frequency of the nodes. In this example, the jobassignor 104 assigns the job to the nodes 109 and 117 and instructs thecontrol processes 111 and 119 to set the processor core operatingfrequencies of the cores 1 113 and 121 and cores 2 115 and 123 to theselected processor core operating frequency.

FIGS. 2 and 3 are flowcharts depicting example operations for selectingfrequencies to run jobs based on energy usage and performance data. Flowbegins at block 201, where a job is received for a cluster. For example,a user submits a job to the cluster using a host system's command lineinterface by typing a name of an executable file that indicates thejob's tasks. As another example, a user submits a job through amanagement interface provided by the host system. The managementinterface allows the user to select tasks for the job and indicate taskdependencies.

At block 203, it is determined if the job has been performed previously.Determining if the job has been performed previously can comprisesearching a performance and energy usage database for a job identifier,searching the performance and energy usage database for similar jobs,etc. In addition, a job scheduler may also determine whether the job wasperformed within a certain preceding time period. If the job has notbeen performed previously, flow continues at block 205. If the job hasbeen performed previously, flow continues at block 301 of FIG. 3.

At block 205, the job has not been performed previously, so the job isrun at a default processor core operating frequency. The job can beperformed at the default processor core operating frequency because Atsome previous time, benchmark tests are run at the default processorcore operating frequency, for example when the cluster was configured.Performance metrics are measured during performance of the job (either aprevious performance or the current performance) benchmark tests andcompared against performance metrics from the benchmark tests so that anappropriate energy model is chosen for the job based on characteristicsof the job. For example, different energy models can be chosen forcomputation intensive jobs and memory intensive jobs because power andenergy usage of memories can be considered in addition to power andenergy usage of processors for memory intensive jobs when determiningoverall power and energy usage. As another example, power and energyusage of network elements (e.g., network adapters, routers, hubs, etc.)could be considered in selecting an energy model for an input/output(I/O) intensive job.

At block 207, performance metrics are measured. Examples of performancemetrics include giga-instructions per second (GIPS), memory bandwidth ingigabytes per second (GBS), translation lookaside buffer (TLB) misses,cycles per instruction (CPI), completion time, etc.

At block 209, coefficients of an energy model are determined based onthe measured performance metrics. The coefficients can be determinedfrom the performance and energy usage database based on the measuredperformance metrics of a benchmark test that most closely resembles thejob (i.e., the characteristics of the job are similar to thecharacteristics of the benchmark test). For example, a record indicatingthe coefficients is located based on matching (within a certain range)benchmark test performance metrics with the job performance metrics.

At block 211, energy usage and performance for each of the supportedfrequencies is estimated based on the coefficients. For example, thepower consumption for each of the supported frequencies are estimatedbased on Expression 1, below. In Expression 1, p represents estimatedpower consumption; a, b, and c, represent coefficients; and i=0, . . . ,n. The default processor core operating frequency is represented by nwhile the 0 to n−1 represent supported frequencies below the defaultprocessor core operating frequency. GIPS and GBS are example performancemetrics discussed at block 207.

p _(i) =a _(i)×GIPS+b _(i)×GBS+c _(i)   Expression 1

Performance for each supported frequency can be estimated based onExpression 2, below. The default processor core operating frequency isrepresented by f_(n) while the f₀ to f_(n−1) represent supportedfrequencies below the default processor core operating frequency, wherei=0, . . . , n. T_(i) represents estimated completion time for eachsupported frequency (f_(i)) and T_(n) represents the completion time ofthe job at the default processor core operating frequency (f_(n)).CPI_(n) represents a measured cycles per instruction of the job at f_(n)and CPI_(i) represents an estimated cycles per instruction at eachExample performance metrics for T_(n) and CPI_(n) are discussed at block207.

$\begin{matrix}{T_{i} = {\frac{T_{n} \times f_{n}}{f_{i}} \times \frac{{CPI}_{n}}{{CPI}_{i}}}} & {{Expression}\mspace{14mu} 2}\end{matrix}$

Cycles per instruction at each supported frequency can be estimatedbased on Expression 3, below. The default processor core operatingfrequency is represented by n while the 0 to n−1 represent supportedfrequencies below the default processor core operating frequency wherei=0, . . . , n. TPI_(n) represents transactions per instruction andCPI_(n) represents a measured cycles per instruction at f_(n), while d,e, and f represent coefficients. TPI_(n) is an example performancemetric discussed at block 207.

CPI_(i) =d _(i)×CPI_(n) +e _(i)×TPI_(n) +f _(i)   Expression 3

Transactions per instruction at the default processor core operatingfrequency can be estimated based on Expression 4. The default processorcore operating frequency is represented by f_(n). GBS and CPI_(n) areexample performance metrics discussed at block 207, and cache_line_sizerepresents a size of cache lines in an instruction cache.

$\begin{matrix}{{TPI}_{n} = \frac{{GBS} \times {CPI}_{n}}{{cache\_ line}{\_ size} \times f_{n}}} & {{Expression}\mspace{14mu} 4}\end{matrix}$

Energy usage for each supported frequency can then be estimated based onmultiplying the estimated completion times by the power consumptions ateach supported frequency.

At block 213, the estimated energy usage and job performance data foreach of the supported frequencies is stored with an indication of thecorresponding supported frequency. The estimated energy usage andperformance can be stored in the performance and energy usage database.

FIG. 3 is a flowchart, which continues from FIG. 2, depicting exampleoperations for selecting frequencies to perform jobs based on energyusage and performance data. Flow continues from block 203 of FIG. 3 atblock 301. The job has been performed previously, so it is determined ifthe job is subject to a policy. The policy can indicate performanceand/or energy usage constraints for the job. For example, a policy mayindicate that energy consumption should be minimized while keepingperformance degradation within an indicated tolerance.

At block 303, energy usage and performance data is determined for thesupported frequencies. The energy usage and performance data can bedetermined from the performance and energy usage database based on anidentifier of the job. Estimates for energy usage and performance foreach supported frequency were computed and stored for a previousperformance of the job, or similar job.

At block 305, it is determined if one of the processor core operatingfrequencies satisfies the policy. For example, the policy specifies thatenergy usage should be reduced by 50 percent while completion time ofthe job should not increase more than 20 percent. The energy aware jobscheduler can determine a processor core operating frequency of thesupported frequencies with an estimated energy usage below 50 percentand an estimated completion time of less than 20 percent degradationbased on the energy usage and performance data. If more than onefrequency satisfies the policy, the job scheduler can chose the lowestsatisfying frequency. If one of the frequencies satisfies the policy,flow continues at block 307. If none of the frequencies satisfy thepolicy, flow continues at block 313. Embodiments can also setfrequencies across nodes or within nodes at different frequencies thatsatisfy the policy and reduce energy consumption. For example, a jobscheduler can determine that energy consumption can be reduced whilesatisfying performance requirements with a lower frequency on a firstnode, a higher frequency on a second node, and both frequencies at athird node. In addition, embodiment can reconcile multiple policies andselect processor core operating frequency(ies) to perform a jobaccordingly. For instance, embodiments can reconcile a job policy thatspecifies a threshold performance degradation of no more than 20% with acluster policy that specifies a particular amount of energy consumptionwithin a 24 hour period.

At block 307, the processor core operating frequency of the nodesassigned to the job is set based on the processor core operatingfrequency that satisfies the policy. For example, the job schedulertransmits instructions to control processes of the nodes that indicatethe satisfying processor core operating frequency. In response, thecontrol processes set the nodes to run at the satisfying frequency.

At block 309, the job is performed at the assigned nodes. For example,the job scheduler can perform any one of provide a reference indicatinga location of code representing the job (or a task within the job) tothe control processes; pass data to the control processes, etc. Inresponse, the control processes initiate performance of the job on theassigned nodes. Actual performance and energy usage can be measuredwhile the job is running The job scheduler can store the actualperformance and energy usage in the performance and energy usagedatabase so that the actual performance and energy usage can be used forselecting frequencies for future performances of the job rather than theestimated performance and energy usage. In addition, the job schedulercan utilize an energy model to update estimates of other supportedfrequencies based on the actual performance and energy usage.

At block 311, the processor core operating frequency of the nodesassigned to the job is returned to the default processor core operatingfrequency. The frequency is returned to the default so that another jobcan be assigned to the node. Returning the processor core operatingfrequency of the nodes to default can comprise transmittinginstructions, an opcode, command, flag, etc., to the control processesindicating that the nodes should run at the default processor coreoperating frequency. Embodiments are not limited to returning a core tothe default processor core operating frequency. Embodiments can leavethe processor core operating frequency unchanged, set the processor coreoperating frequency to the lowest processor core operating frequency,etc.

At block 313, the job was not subject to a policy or none of theprocessor core operating frequencies satisfied the policy, so the job isperformed at default processor core operating frequency. Although thejob can be performed at the default processor core operating frequency,embodiments are not limited to performing the job at the defaultprocessor core operating frequency. If the job was not subject to apolicy, the job can be run at any processor core operating frequency.The job scheduler can determine the processor core operating frequencybased on current/projected workloads, overall power usage of a cluster,etc. If none of the processor core operating frequencies satisfied thepolicy, the job may be run at a frequency that best satisfies thepolicy.

Although embodiments refer to performing jobs at different frequencies,embodiments are not so limited. In some embodiments, other energyreduction techniques (e.g., memory throttling, powering down peripheralsassociated with the nodes that will not be used for a job, etc.) can beutilized in addition to frequency scaling.

The examples above refer to using estimated data and coefficients ofenergy models. Estimated energy usage data can be computed based on anenergy usage regression model. Coefficients of the regression model canbe determined when a cluster is configured. Energy usage and performancemetrics can be measured while a set of benchmarks is run on nodes in thecluster. The coefficients can be determined based on the measured energyusage and performance metrics. FIG. 4 is a flowchart depicting exampleoperations for determining coefficients of a regression model. Flowbegins at block 401, where nodes in a cluster are determined. The nodesin the cluster can be determined during configuration of the cluster.

At block 403, a loop begins for each node.

At block 405, a loop begins for each supported frequency of the node.

At block 407, benchmark tests are run on the node. To run the benchmarktests, a job scheduler can indicate the benchmark tests (e.g., byproviding references to the benchmark tests) and the frequency to acontrol process associated with the node. In response, the controlprocess can initiate execution of the benchmark tests at the indicatedprocessor core operating frequency. The benchmark tests can be based onapplication workloads defined in Standard Performance EvaluationCorporation (SPEC) CFP2006 benchmarks. The benchmark tests can be basedon representative workloads (e.g., computation intensive, memoryintensive, I/O intensive, etc.).

At block 409, it is determined if the node is running at defaultprocessor core operating frequency. Performance metrics can be measuredat the default processor core operating frequency and can be differentfor different types of workloads (i.e., memory intensive versuscomputation intensive). The performance metrics measured duringbenchmark testing can be matched to measured performance metrics for ajob the first time the job is performed so that energy usage andperformance can be estimated with an appropriate model based on thejob's workload (i.e., the job is matched to one of the benchmark teststhat most closely resembles the workload of the job). If the node isrunning at default processor core operating frequency, flow continues atblock 411. If the node is not running at default processor coreoperating frequency, flow continues at block 415.

At block 411, the node is running at default processor core operatingfrequency, so performance is measured. Examples of performance metricsinclude giga-instructions per second (GIPS), memory bandwidth ingigabytes per second (GBS), translation lookaside buffer (TLB) misses,cycles per instruction (CPI), completion time, etc.

At block 413, the performance metrics are stored. The performancemetrics can be stored in a performance and energy usage database.

At block 415, power consumption and CPI are measured. The powerconsumption and CPI can be measured at all supported frequencies, lessthan all supported frequencies, randomly selected supported frequencies,preselected supported frequencies, etc. Power consumption can bemeasured by AEM. The power consumption can include power consumed byperipherals (e.g., cooling systems, storage devices, etc.) associatedwith the node. CPI can be determined based on an average number ofcycles used for each instruction executed during the benchmark tests.

At block 417, the power consumption is stored with an indication of thefrequency in the performance and energy usage database.

At block 419, the loop for each supported frequency ends.

At block 421, coefficients of the energy model are computed based on thepower consumption and performance metrics. Coefficients can be computedfor each supported frequency based on Expressions 1 and 3. InExpressions 1 and 3, the default processor core operating frequency isrepresented by n while 0 to n−1 represent supported frequencies belowthe default processor core operating frequency, where i=0, . . . , n. InExpression 1, p represents measured power consumption at each supportedfrequency, i. In Expression 3, CPI_(i) represents measured cycles perinstruction at each supported frequency, i. TPI_(n) can be computedbased on Expression 4. The coefficients are represented by a, b, c, d,and e, GIPS and GBS are performance metrics measured in block 413, andcache_line_size represents a size of cache lines in an instructioncache.

$\begin{matrix}{p_{i} = {{a_{i} \times {GIPS}} + {b_{i} \times {GBS}} + {c_{i}({restated})}}} & {{Expression}\mspace{14mu} 1} \\{{CPI}_{i} = {{d_{i} \times {CPI}_{n}} + {e_{i} \times {TPI}_{n}} + {f_{i}({restated})}}} & {{Expression}\mspace{14mu} 3} \\{{{TPI}_{n} = \frac{{GBS} \times {CPI}_{n}}{{cache\_ line}{\_ size} \times f_{n}}}({restated})} & {{Expression}\mspace{14mu} 4}\end{matrix}$

At block 423, the coefficients are stored. The coefficients can bestored with an indication of the performance metrics. When a job isperformed, performance metrics can be measured and matched toperformance metrics measured during benchmark testing in the performanceand energy usage database so that appropriate coefficients can belocated in the database and utilized when estimating performance andenergy usage of the job.

At block 425, the loop for each node ends.

Embodiments are not limited to the example flowcharts depicted in theabove figures. Embodiments can perform additional operations, feweroperations, operations in parallel, etc. For instance, referring to FIG.4, the operations for running benchmark tests and measuring performancemetrics and power consumption for each node can be run in parallel. Inaddition, operations can be performed to select energy usage andperformance data for a previous run of a job and similar jobs. A jobscheduler can use data from a previous run of the job at a first set offrequencies and data from similar previously run jobs at other supportedfrequencies. Operations can also be performed to compare data ofdifferent types of nodes, which support different frequencies, whenselecting a node for job scheduling.

As will be appreciated by one skilled in the art, aspects of the presentinventive subject matter may be embodied as a system, method or computerprogram product. Accordingly, aspects of the present inventive subjectmatter may take the form of an entirely hardware embodiment, a softwareembodiment (including firmware, resident software, micro-code, etc.) oran embodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present inventive subject matter may takethe form of a computer program product embodied in one or more computerreadable medium(s) having computer readable program code embodiedthereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent inventive subject matter may be written in any combination ofone or more programming languages, including an object orientedprogramming language such as Java, Smalltalk, C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present inventive subject matter are described withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems) and computer program products according toembodiments of the inventive subject matter. It will be understood thateach block of the flowchart illustrations and/or block diagrams, andcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer program instructions. Thesecomputer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

FIG. 5 depicts an example computer system with an energy aware jobscheduler. A computer system includes a processor unit 501 (possiblyincluding multiple processors, multiple cores, multiple nodes, and/orimplementing multi-threading, etc.). The computer system includes memory507. The memory 507 may be system memory (e.g., one or more of cache,SRAM, DRAM, zero capacitor RAM, Twin Transistor RAM, eDRAM, EDO RAM, DDRRAM, EEPROM, NRAM, RRAM, SONOS, PRAM, etc.) or any one or more of theabove already described possible realizations of machine-readable media.The computer system also includes a bus 503 (e.g., PCI bus, ISA bus,PCI-Express bus, HyperTransport® bus, InfiniBand® bus, NuBus bus, etc.),a network interface 505 (e.g., an ATM interface, an Ethernet interface,a Frame Relay interface, SONET interface, wireless interface, etc.), anda storage device(s) 509 (e.g., optical storage, magnetic storage, etc.).The computer system also includes an energy aware job scheduler 521. Theenergy aware job scheduler 521 analyzes energy usage and job performancedata to select a processor core operating frequency to perform a job ona node in a cluster in accordance with a policy for the job. Any one ofthese functionalities may be partially (or entirely) implemented inhardware and/or on the processing unit 501. For example, thefunctionality may be implemented with an application specific integratedcircuit, in logic implemented in the processing unit 501, in aco-processor on a peripheral device or card, etc. Further, realizationsmay include fewer or additional components not illustrated in FIG. 5(e.g., video cards, audio cards, additional network interfaces,peripheral devices, etc.). The processor unit 501, the storage device(s)509, and the network interface 505 are coupled to the bus 503. Althoughillustrated as being coupled to the bus 503, the memory 507 may becoupled to the processor unit 501.

While the embodiments are described with reference to variousimplementations and exploitations, it will be understood that theseembodiments are illustrative and that the scope of the inventive subjectmatter is not limited to them. For instance, the above examples refer todetermining whether a job or similar job has been previously performedin a cluster. Embodiments can, however, utilize energy and usage datafor the job or a similar job performed in a different cluster or a nodenot within a cluster. Embodiments can access energy usage and jobperformance data independent of the cluster and utilize this data,perhaps based on node similarity, to perform the requested job. Ingeneral, techniques for energy-aware job scheduling as described hereinmay be implemented with facilities consistent with any hardware systemor hardware systems. Many variations, modifications, additions, andimprovements are possible.

Plural instances may be provided for components, operations orstructures described herein as a single instance. Finally, boundariesbetween various components, operations and data stores are somewhatarbitrary, and particular operations are illustrated in the context ofspecific illustrative configurations. Other allocations of functionalityare envisioned and may fall within the scope of the inventive subjectmatter. In general, structures and functionality presented as separatecomponents in the exemplary configurations may be implemented as acombined structure or component. Similarly, structures and functionalitypresented as a single component may be implemented as separatecomponents. These and other variations, modifications, additions, andimprovements may fall within the scope of the inventive subject matter.

1. A method comprising: accessing data that specifies energy usage and job performance metrics that correspond to a job and a plurality of processor core operating frequencies, wherein the job has been requested of a cluster; selecting a first of the plurality of processor core operating frequencies that satisfies an energy usage criterion for performing the job based, at least in part, on the data that specifies energy usage and job performance metrics that correspond to the job; and assigning the job to be performed by a node in the cluster at the selected first of the plurality of processor core operating frequencies.
 2. The method of claim 1 further comprising determining that the job or a similar job has previously been performed.
 3. The method of claim 1, wherein the energy usage criterion for performing the job indicates at least one of a maximum amount of energy to be used to perform the job and an energy conservation goal.
 4. The method of claim 1, wherein the plurality of processor core operating frequencies comprises a default processor core operating frequencies, and wherein the first of the plurality of processor core operating frequencies is lower than the default processor core operating frequency.
 5. The method of claim 4, wherein said assigning the job to be performed by the node in the cluster at the first of the plurality of processor core operating frequencies comprises: setting at least a first processor core of the node to run at the first of the plurality of processor core operating frequencies.
 6. The method of claim 4 further comprising: prior to said selecting the first of the plurality of processor core operating frequencies that satisfies the energy usage criterion for performing the job, collecting energy usage and performance metrics for the job performed in the cluster at the default processor core operating frequency; determining coefficients of an energy model based on the performance metrics and energy usage; estimating energy usage and performance metrics for the job at the first of the plurality of processor core operating frequencies based on the coefficients and the energy model; and storing the estimated energy usage and performance metrics for the job at the first of the plurality of processor core operating frequencies; and associating the stored estimated energy usage and performance metrics with the job and with the first of the plurality of processor core operating frequencies.
 7. The method of claim 1 further comprising: determining that a performance constraint is specified for the job; wherein said selecting the first of the plurality of processor core operating frequencies that also satisfies the performance constraint.
 8. The method of claim 1 further comprising: measuring actual energy usage and performance metrics while the job is performed by the node at the first of the plurality of processor core operating frequencies; and updating the data with the actual energy usage and performance metrics. 